Bart's way to create bootable CD-Roms

Welcome to world's #1 page about creating bootable CD-Roms for PC!

Page contents

Introduction

For whom is this page?

This page is for you if you want to:

• create bootable CD-Roms on a regular basis
• build and burn fully automatic (optional blank CDRW before burn)
• use only freeware software to create your CDs
• create a bootable CD-Rom with multiple boot images
• create a Dos bootable CD-Rom using a hardware independent CD-Rom driver (for SCSI and ATAPI)

• you want to create just 1 simple bootable CD-Rom. You should use Cdrwin, Nero or any other well known application to create CDs
• you do not understand basic things like;
  
  • difference between a bootdisk and a boot image
  • CDR, CDRW medium
  • unpacking, copying, editing or renaming files

What is a bootable CD-Rom?

1. PC running Windows 98/ME, Windows NT 4.0 SP4+, Windows 2000 or Windows XP.
2. SCSI or ATAPI based CD-recorder or rewriter.
3. ASPI manager (see also: Bart's page about ASPI).
4. 1 recordable (CDR) or rewritable (CDRW) CD, on first try, use a rewritable if you can.
5. To test if the completed CD works, you'll need a PC capable of booting CD-Roms.
6. Some basic skills for copying, unpacking and editing some files.

1. If you have not already setup cdrpack version 1.3 then download cdrpack v1.3 (~640KB).
   This file contains a workspace where you can build your bootable CD's from.
   Unpack the cdrpack13.zip file to a directory on your local harddisk.
   Make sure you expand the subdirectories! So when using pkunzip.exe use the -d option!
   
   
2. Download single eltorito add-on. Unpack the single_eltorito_addon.zip file into the same directory as cdrpack 1.3.
   Make sure you expand the subdirectories! So when using pkunzip.exe use the -d option!
   
   
3. Follow the steps in the CDBOOT page to create the CDBOOT bootdisk.
   Create a boot image file from the "CDBOOT" bootdisk using dd.exe, you should call this boot image "cdboot.img" and put it into the "cds\single_eltorito\disk1" directory.
   Note! You have to rename the boot image to lowercase!
   
   
4. Change cds\single_eltorito\disk1\autorun.bat you can add any commands you want. For example start an application from CD-Rom.
   
   
5. All other files and folders you want in the CD-Rom filesystem must also be copied into cds\single_eltorito\disk1 directory.
   
   
6. Edit the file cds\single_eltorito\disk1\build.mak and put your name into the "preparer" variable.
   
   
7. Start the batch file "run.bat".
   From the "Main menu" select "Build & Burn" and "single_eltorito".
   
   

1. If you have not already setup cdrpack version 1.3 then download cdrpack v1.3 (~640KB).
   This file contains a workspace where you can build your bootable CD's from.
   Unpack the cdrpack13.zip file to a directory on your local harddisk.
   Make sure you expand the subdirectories! So when using pkunzip.exe use the -d option!
   
   
2. If you have not already setup diskemu add-on, version 1.1 (11/07/01) then download diskemu add-on (~9KB).
   Unpack the diskemu_addon.zip file into the same directory as cdrpack 1.3.
   Make sure you expand the subdirectories! So when using pkunzip.exe use the -d option!
   
   
3. Download single diskemu add-on. Unpack the single_diskemu_addon.zip file into the same directory as cdrpack 1.3.
   Make sure you expand the subdirectories! So when using pkunzip.exe use the -d option!
   
   
4. Follow the steps in the ELBOOT page to create the ELBOOT bootdisk.
   Create a boot image file from the "ELBOOT" bootdisk using dd.exe, you should call this boot image "elboot.img" and put it into the "cds\single_diskemu\disk1" directory.
   Note! You have to rename the boot image to lowercase!
   
   
5. All other files and folders you want in the CD-Rom filesystem must also be copied into cds\single_diskemu\disk1 directory.
   
   
6. Customize the file cds\single_diskemu\disk1\diskemu.cmd for your personal needs.
   
   
7. Change cds\single_diskemu\disk1\autorun.bat you can add any commands you want. For example start an application from CD-Rom.
   
   
8. Edit the file cds\single_diskemu\disk1\build.mak and put your name into the "preparer" variable.
   
   
9. Start the batch file "run.bat".
   From the "Main menu" select "Build & Burn" and "single_diskemu".
   
   

Warning!

• cdboot.img - CDBOOT bootdisk
• msclient.img - Microsoft Client TCP/IP bootdisk
• scsitool.img - SCSITOOL bootdisk
• cpuid.img - The Intel® Processor Frequency ID Utility

1. If you have not already setup cdrpack version 1.3 then download cdrpack v1.3 (~640KB).
   This file contains a workspace where you can build your bootable CD's from.
   Unpack the cdrpack13.zip file to a directory on your local harddisk.
   Make sure you expand the subdirectories! So when using pkunzip.exe use the -d option!
   
   
2. Download multi eltorito add-on. Unpack the multi_eltorito_addon.zip file into the same directory as cdrpack 1.3.
   Make sure you expand the subdirectories! So when using pkunzip.exe use the -d option!
   
   
3. Follow the steps in the CDBOOT page to create the CDBOOT bootdisk.
   Create a boot image file from the "CDBOOT" bootdisk using dd.exe, you should call this boot image "cdboot.img" and put it into the "cds\multi_eltorito\disk1" directory.
   Note! You have to rename the boot image to lowercase!
   
   
4. Follow the steps in the MSClient page to create the MSClient bootdisk.
   Create a boot image file from the "MSClient" bootdisk using dd.exe, you should call this boot image "msclient.img" and put it into the "cds\multi_eltorito\disk1" directory.
   Note! You have to rename the boot image to lowercase!
   
   
5. Follow the steps in the SCSITOOL page to create the SCSITOOL bootdisk.
   Create a boot image file from the "SCSITOOL" bootdisk using dd.exe, you should call this boot image "scsitool.img" and put it into the "cds\multi_eltorito\disk1" directory.
   Note! You have to rename the boot image to lowercase!
   
   
6. Follow the steps in the CPUID page to create the CPUID bootdisk.
   Create a boot image file from the "CPUID" bootdisk using dd.exe, you should call this boot image "cpuid.img" and put it into the "cds\multi_eltorito\disk1" directory.
   Note! You have to rename the boot image to lowercase!
   
   
7. All other files and folders you want in the CD-Rom filesystem must also be copied into cds\multi_eltorito\disk1 directory.
   
   
8. Change cds\multi_eltorito\disk1\autorun.bat you can add any commands you want. For example start an application from CD-Rom.
   
   
9. Edit the file cds\multi_eltorito\disk1\build.mak and put your name into the "preparer" variable.
   
   
10. Start the batch file "run.bat".
    From the "Main menu" select "Build & Burn" and "multi_eltorito".
    
    

1. If you have not already setup cdrpack version 1.3 then download cdrpack v1.3 (~640KB).
   This file contains a workspace where you can build your bootable CD's from.
   Unpack the cdrpack13.zip file to a directory on your local harddisk.
   Make sure you expand the subdirectories! So when using pkunzip.exe use the -d option!
   
   
2. Download Windows NT 4.0 add-on. Unpack the nt4_addon.zip file into the same directory as cdrpack 1.3.
   Make sure you expand the subdirectories! So when using pkunzip.exe use the -d option!
   
   The add-on contains, the Windows 2000 bootstrap loader, the Windows 2000 bootfix.bin and the "build.mak" file.
   We will be using the bootstrap loader from Windows 2000, this will give us the "Press any key to boot from CD" option.
   
   
3. From Windows NT 4.0 CD copy the "i386" folder to cds\nt4ws_us\disk1\.
   You will find the cds\nt4ws_us\disk1\ folder in the same directory as where you have unpacked the cdrpack and Windows NT 4.0 add-on.
   
   
4. From Windows NT 4.0 CD copy into cds\nt4ws_us\disk1\ the following files:
   If you are building a Windows NT 4.0 workstation CD copy: cdrom_w.40
   If you are building a Windows NT 4.0 server CD copy: cdrom_s.40
   
   
   
5. Optionally copy (from Windows NT 4.0 CD) into cds\nt4ws_us\disk1\ the following files:
   autorun.inf
   
   
6. If you have copied Windows NT 4.0 from MSDN CD...
   Edit the file i386/txtsetup.sif
   section [SetupData], and change SetupSourcePath = "\"
   
   
7. Copy Service Pack 6a, the Post-SP6a Security Rollup Package (SRP) and maybe some other security fixes to cds\nt4ws_us\disk1\.
   
   
8. Update Atapi driver.
   
   Unpack Service Pack 6a to a temporarily folder using /x parameter.
   From this temporarily folder copy into cds\nt4ws_us\disk1\i386 the following files:
   
   • ntldr
   • ntdetect.com
   • atapi.sys
   
   
9. All other files and folders you want in the CD-Rom filesystem must also be added to cds\nt4ws_us\disk1.
   Things you could add are: latest internet explorer, directx, ...
   
   
10. Edit the file cds\nt4ws_us\build.mak change the "volumeid" if you like and put your name into the "preparer" variable.
    
    
11. Let's check some files to see if they are in the right place.
    Make sure that the following files exist:
    
    • cds\nt4ws_us\disk1\w2ksect.dat
    • cds\nt4ws_us\disk1\i386\bootfix.bin
    • cds\nt4ws_us\disk1\i386\setupldr.bin
    • If you are building a Windows NT 4.0 workstation CD: cds\nt4ws_us\disk1\cdrom_w.40
      If you are building a Windows NT 4.0 server CD: cds\nt4ws_us\disk1\cdrom_s.40
      
    
    If one or more files are missing do not continue! Go back to correct it!
    
    
12. Start the batch file "run.bat".
    From the "Main menu" select "Build & Burn" and "nt4ws_us".
    
    

1. If you have not already setup cdrpack version 1.3 then download cdrpack v1.3 (~640KB).
   This file contains a workspace where you can build your bootable CD's from.
   Unpack the cdrpack13.zip file to a directory on your local harddisk.
   Make sure you expand the subdirectories! So when using pkunzip.exe use the -d option!
   
   
2. Download Windows 2000 add-on. Unpack the w2k_addon.zip file into the same directory as cdrpack 1.3.
   Make sure you expand the subdirectories! So when using pkunzip.exe use the -d option!
   
   The add-on contains, the Windows 2000 bootstrap loader and the "build.mak" file.
   
   
3. From Windows 2000 CD copy the "i386" folder to cds\w2kpro_us\disk1\.
   You will find the cds\w2kpro_us\disk1\ folder in the same directory as where you have unpacked the cdrpack and Windows 2000 add-on.
   
   
4. From Windows 2000 CD copy into cds\w2kpro_us\disk1\ the following files:
   Always copy: cdrom_nt.5
   If you are building a Windows 2000 professional CD copy: cdrom_ip.5
   If you are building a Windows 2000 server CD copy: cdrom_is.5
   If you are building a Windows 2000 advanced server CD copy: cdrom_ia.5
   
   Note! Be sure only one "CDROM_Ix.5" file is in the root!
   
   
5. Optionally copy (from Windows 2000 CD) into cds\w2kpro_us\disk1\ the following files:
   autorun.inf
   read1st.txt
   readme.doc
   setup.exe
   
   
6. If you have copied windows 2000 from MSDN CD...
   Edit the file i386/txtsetup.sif
   section [SetupData], and change the setup source path, it should read: SetupSourcePath = "\"
   
   
7. If you have copied windows 2000 from MSDN CD you can disable the product key prompt:
   Edit i386/setupp.ini file, remove the read-only attribute and open the file in notepad.
   
   Change the last 3 digits of the Pid number to 270
   Example:
   [Pid]
   ExtraData=123456789012345678901234567890
   Pid=12345270
   
   
8. You can apply the latest Windows 2000 Service Pack to this installation (integrated installation). So that you have an installation CD-ROM with the service pack build in.
   Extract the files from your service pack files using the "/x" parameter.
   
   For example: w2kspx.exe /x
   (where x is your service pack level)
   
   Apply the service pack to the files in the "cds\w2kpro_us\disk1\i386" directory using "update.exe" with the "-s" option (you must supply full path).
   
   For example: update.exe -s:c:\bootcd\cds\w2kpro_us\disk1\
   
   The update.exe can only be started on a Windows 2000 PC!
   
   Be sure to check that the following file exists: cds\w2kpro_us\disk1\cdrom_sp.tst or cds\w2kpro_us\disk1\cdromspx.tst
   (where x is your service pack level)
   
   
9. Copy the latest Service Pack and security patches to cds\w2kpro_us\disk1\.
   You should do this even if you have done "integraded installation" so that you can use this CD to update existing win2k machines to the latest Service Pack.
   
   
10. All other files and folders you want in the CD-Rom filesystem must also be added to cds\w2kpro_us\disk1.
    Things you could add are: latest internet explorer, directx, ...
    
    
11. Edit the file cds\w2kpro_us\build.mak change the "volumeid" if you like and put your name into the "preparer" variable.
    
    
12. Let's check some files to see if they are in the right place.
    Make sure that the following files exist:
    
    • cds\w2kpro_us\disk1\w2ksect.dat
    • cds\w2kpro_us\disk1\i386\bootfix.bin
    • cds\w2kpro_us\disk1\i386\setupldr.bin
    • cds\w2kpro_us\disk1\cdrom_nt.5
    • If you are building a Windows 2000 professional CD: cds\w2kpro_us\disk1\cdrom_ip.5
      If you are building a Windows 2000 server CD: cds\w2kpro_us\disk1\cdrom_is.5
      If you are building a Windows 2000 advanced server CD: cds\w2kpro_us\disk1\cdrom_ia.5
    • If Service Pack 1: cds\w2kpro_us\disk1\cdrom_sp.tst
      If Service Pack 2 (or higher): cds\w2kpro_us\disk1\cdromspx.tst
      (where x is your service pack level)
    
    If one or more files are missing do not continue! Go back to correct it!
    
    
13. Start the batch file "run.bat".
    From the "Main menu" select "Build & Burn" and "w2kpro_us".
    
    

1. If you have not already setup cdrpack version 1.3 then download cdrpack v1.3 (~640KB).
   This file contains a workspace where you can build your bootable CD's from.
   Unpack the cdrpack13.zip file to a directory on your local harddisk.
   Make sure you expand the subdirectories! So when using pkunzip.exe use the -d option!
   
   
2. Download Windows XP add-on. Unpack the wxp_addon.zip file into the same directory as cdrpack 1.3.
   Make sure you expand the subdirectories! So when using pkunzip.exe use the -d option!
   
   The add-on contains, the Windows XP bootstrap loader (same as Windows 2000) and the "build.mak" file.
   
   
3. Copy from your Windows XP CD the "i386" folder to cds\wxppro_us\disk1\.
   You will find the cds\wxppro_us\disk1\ folder in the same directory as where you have unpacked the cdrpack and Windows XP addon.
   
   The location of the i386 folder may differ, for example when you have a dual boot MSDN cd-rom it will be in \%lang%\winxp\%edition%, where %lang% is your language, like "ENGLISH", "GERMAN" and %edition% is "Home" or "Pro". Other CD's may have it just in the root or in some other location.
   
   
4. Copy from Windows XP CD into cds\wxppro_us\disk1\ the following files:
   Always copy: win51
   If you are building a Windows XP Home edition CD copy: win51ic
   If you are building a Windows XP Professional CD copy: win51ip
   
   
5. Optionally copy (from Windows XP CD) into cds\wxppro_us\disk1\ the following files:
   AUTORUN.INF
   README.HTM
   SETUP.EXE
   
   
6. Edit the file i386/txtsetup.sif
   section [SetupData], and change (or verify) SetupSourcePath = "\"
   
   
7. Copy the latest security patches to cds\wxppro_us\disk1\.
   
   
8. All other files and folders you want in the CD-Rom filesystem must also be added to cds\wxppro_us\disk1.
   Things you could add are: latest internet explorer, directx, ...
   
   
9. Edit the file cds\wxppro_us\build.mak change the "volumeid" if you like and put your name into the "preparer" variable.
   
   
10. Let's check some files to see if they are in the right place.
    Make sure that the following files exist:
    
    • cds\wxppro_us\disk1\w2ksect.dat
    • cds\wxppro_us\disk1\i386\bootfix.bin
    • cds\wxppro_us\disk1\i386\setupldr.bin
    • cds\wxppro_us\disk1\win51
    • If you are building a Windows XP Home edition CD: cds\wxppro_us\disk1\win51ic
      If you are building a Windows XP Professional CD: cds\wxppro_us\disk1\win51ip
      
    
    If one or more files are missing do not continue! Go back to correct it!
    
    
11. Start the batch file "run.bat".
    From the "Main menu" select "Build & Burn" and "wxppro_us".
    
    

• Norton Ghost (from symantec)

----------------------------------------------------------------------------
ELGHOST created by Bart Lagerweij                          http://www.nu2.nu
----------------------------------------------------------------------------

These are the description lines taken from the hdimage.txt file.
It can help you remember what was in this hdimage.gho file.
Will you remember it next month?

Copy disk image from CD-Rom to harddisk !!!

Continue? [Y,N] : y


This will erase all data currently on your harddisk !!!

Type "agree" to confirm this action.

Type here :

1. If you have not already setup cdrpack version 1.3 then download cdrpack v1.3 (~640KB).
   This file contains a workspace where you can build your bootable CD's from.
   Unpack the cdrpack13.zip file to a directory on your local harddisk.
   Make sure you expand the subdirectories! So when using pkunzip.exe use the -d option!
   
   
2. If you have not already setup diskemu add-on, version 1.1 (11/07/01) then download diskemu add-on (~9KB).
   Unpack the diskemu_addon.zip file into the same directory as cdrpack 1.3.
   Make sure you expand the subdirectories! So when using pkunzip.exe use the -d option!
   
   
3. Download elghost add-on. Unpack the elghost_addon.zip file into the same directory as cdrpack 1.3.
   Make sure you expand the subdirectories! So when using pkunzip.exe use the -d option!
   
   
4. Follow the steps in section ELBOOT to create the ELBOOT boot diskette.
   Create an image file from the "elboot" diskette using dd.exe, you should call this file "elboot.img" and put it into the "cds\elghost\disk1" directory.
   
   
5. Copy ghost.exe (not included, not freeware!) to cds\elghost\disk1
   
   
6. Copy your ghost image file to cds\elghost\disk1\hdimage.gho it must be called "hdimage.gho" !
   
   
7. Create a text file called "cds\elghost\disk1\hdimage.txt" with a short description (2-8 lines of plain text) about the ghost image. It must be called "hdimage.txt" !
   
   
8. Edit the file cds\elghost\disk1\build.mak and put your name into the "preparer" variable.
   
   
9. Start the batch file "run.bat".
   From the "Main menu" select "Build & Burn" and "elghost".
   
   

1. Format a bootable Dos 6.x or 7.x floppy diskette (you will need todo this on a Dos 6.x or Windows 9x/ME workstation!).
   format a: /u /s
2. For Dos 7.x: delete the drvspace.bin file (we don't need it)
   attrib -s -h -r drvspace.bin
   del drvspace.bin
3. Copy the following files to your floppy disc:
   
   • EMM386.EXE
   • HIMEM.SYS
   • MSCDEX.EXE
   • DOSKEY.COM
   
   The files below are not required but can be handy:
   
   • FDISK.EXE
   • FORMAT.COM
   • SYS.COM
   • XCOPY.EXE, (for Dos 7.x also XCOPY32.EXE and for win98 also XCOPY32.MOD)
4. Download elboot.zip (~16KB). Unpack elboot.zip file to floppy.
   

When running mkisofs you will receive a message saying: "Warning: creating filesystem that does not conform to ISO-9660." This should be no problem.

For more information on mkisofs v1.13 see the online man page.
Homepage: http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/cdrecord.html
Mkisofs is written by Joerg Schilling.

About mkbootcd.exe

Keynum  : 99999
License : AA999999
MaxPCs  : 99
Name    : YourName
Address1: YourCompany
Address2:
switches: load=y,dump=n,disk=n,peer=n,write=y,fprnt=y

If your ghost image is larger than 620MB it will not fit on your CD. To split it into smaller segments you can use ghost explorer to split it.

More Ghost command-line switches? Look here.

If you don't want Ghost to write any error information to ghost.err, add the "-afile=NUL" switch.

Frequently asked questions

1. [Q] Does Bart's way to create bootable CD-Roms also work on ATAPI/IDE cdwriters?
   
   [A] Yes (still need Aspi manager).
   

2. [Q] I get this message, what does it mean?

   cdrecord: Cannot do inquiry for CD/DVD-Recorder.
   cdrecord: Invalid argument. test unit ready: scsi sendcmd: fatal error
   CDB:  00 00 00 00 00 00
   cmd finished after 0.000s timeout 40s
   

   
   [A] It means that cdrecord is addressing the wrong drive.
   

3. [Q] Could you just save those boot CDs you made as ISO's and have them available for download? That would be great.
   
   [A] Maybe it would be great. But those ISO image would also contain files that are protected by copyright, so it's illegal. It would also flood the link to the internet, because of these large files.
   In other words: NO!. You have to create them yourself.
   

4. [Q] I have create a multi-boot CD, but my computer automatically boots into the first image. What did I do wrong?
   
   [A] This is the most asked question (or problem)! Some people seem to think that they did something wrong, but it is the BIOS in their PC that is propably not supporting multiboot images.
   
   But... there is a way around this! As of Nov 8, 2000 Gary Tong started writing a Bootable CD-Rom Disk Emulator and Dos CD-Rom driver that worked its way around this problem. Currently this project is developed by Bart Lagerweij (that's me).
   Go here: Bootable CD-Rom Disk Emulator.
   

5. [Q] I have a bootable Windows 2000 install/setup CD-Rom, when it boots you must press a key to boot from CD-Rom. If no key was pressed it boots from the hard drive. Is there a way to do the same thing on a bootable CD using a floppy boot image?
   
   [A] Yes, two options:
   1. This can be done using Diskemu.
   2. Use the jo.sys loader I've created.

6. [Q] Mkisofs says: "Warning: creating filesystem that does not conform to ISO-9660"
   
   [A] This is normal, ignore it.
   

7. [Q] Can I emulate writing CDs using cdrecord?
   
   [A] Yes, add the "-dummy" option to cdrecord. This executes everything with the laser turned off.
   

8. [Q] Can I blank a CDRW using cdrecord?
   
   [A] Yes. use the "blank" option in cdrecord.exe
   For a "fast" erase: cdrecord dev=x,y,z blank=fast
   For a "full" erase: cdrecord dev=x,y,z blank=all
   
   When using cdrpack there is a checkbox called "Blank CDRW media before recording" just check it before burning...
   

9. [Q] How can I see what's inside a .ISO file?
   
   [A] Use ISOINFO or IsoBuster.
   
   To see the information from the primary volume descriptor:
   isoinfo -d -i mycd.iso
   
   To see all the files in the ISO image
   isoinfo -l -i mycd.iso
   

10. [Q] I have created a multi boot CD, is it possible to name the items as they come up? (I only see numbers)
    
    [A] No, your BIOS is limited in this way. It just displays the numbers and media types.
    There is only one way around this: use diskem1x.
    

11. [Q] Is it possible to make a bootable CD that will completely boot up Microsoft Windows 9x or NT, as if it was booting from the hard drive?
    
    [A] Yes, it is possible (not easy!)
    
    • For Windows 9x, checkout c't 11/99, page 206 - Booting Windows From CD-Rom.
      (some people have trouble doing this for windows 98, so you should try windows 95).
      
    • For Windows NT4.0, you will need a special version of Windows NT 4.0 called Windows NT Embedded. This is a minimal version of Windows NT4.0 (service pack 5 integrated) with special target design tools. There is an evaluation kit available for a small price.
      (Anybody tried "Whistler Embedded" Beta 1?)
      

12. [Q] I don't have a 2.88MB floppy drive. How do I make a bootable 2.88MB Dos-based floppy image?
    
    [A] You can make a 2.88MB (or any other standard size) floppy image using MKBT, checkout here.
    

13. [Q] The information on this page is a real lifesaver...
    How can I thank Bart for his help?
    How can I do something back?
    
    [A] Look here: http://www.nu2.nu/thanks/bart/.
    

14. [Q] When building the ISO file I get this message: "mkisofs.exe: Uh oh, I cant find the boot image '%file%.img' !"
    (where %file% is the name of your boot image)
    
    [A] Mkisofs.exe cannot find the bootimage file, remember that mkisofs.exe is a Posix/Unix application and it is case sensitive. Try renaming your file into lowercase...
    

15. [Q] I've burned a bootable NT4/W2K/XP CD-Rom using Nero. When booting I can get the message "BOOT: Couldn't find NTLDR"
    
    [A] You need to disable ISO9660 file versions, in Nero you need to do a registry setting:
    HKEY_CURRENT_USER\Software\ahead\Nero - Burning Rom\General\AddISOFileVersion
    Set the value to 0 (zero).
    

• 0.10 Example1 step 5: typing error fixed (forgot "disk1") in mkisofs line (oops)
• 0.11 The URL for Rawrite2.exe was not correct, fixed
• 0.12 Tested Windows98/ATAPI by Hassan. Some very small changes.
• 0.13 Added a note on mkisofs multiboot. Some very small changes.
• 0.14 Changed getting NT aspi32.
• 0.15 Added example3.
• 0.16 Added example4.
• 0.17 Changed example4 for W2K SP1 integrated installation and minor changes.
• 0.18 Changed makedisk.bat, added the "-no-iso-translate" and "-l" option to mkisofs.exe.
  Without the "-no-iso-translate" option mkisofs.exe removes "~" from the original filenames and the "-l" option is for use of long filenames.
• 0.19 Added the text "To prevent typing errors, copy and past it!".
• 0.20 Added "faq" and more user responses.
• 0.21 Added 2 faq's
• 0.22 Added example5: Bootable Ghost restore CD-Rom "ELGHOST". Almost the whole page is changed, dropped the makedisk.bat file, now using a makefile. Added about section (still need to add some more abouts).
• 0.23 Fixed "ifdef publisher" in makefile. Dropped pathlist.txt file.
• 0.24 There was a problem using windows 9x and mkbootcd.exe. When running make.exe it stopped when running mkbootcd.exe (stdin redirect failed). I recompiled mkbootcd v1.02 (which comes as a 16-bit Dos executable) into a win32 executable, problem solved.
• 0.25 Changed all links that went through download.asp to direct-links.
• 0.26 Updated example5 (elghost) to work with the new version of diskemu.bin (v0.5 beta).
• 0.27 Added "about ghost" and "about bootcat".
• 0.28 Added more faq's.
• 0.29 Added faq's and a link.
• 0.30 Updated faq. Numbered faq items for easier reference. Fixed some links.
• 0.31 Updated faq.
• 0.32 Updated faq and did some minor changes.
• 0.33 Updated links and some text for cdrtools v1.10 and make v3.29.1 update.
  Also updated the makefile to v1.4, this should solve "/bin/sh.exe: Command not found" issues.
• 0.34 Updated the makefile to v1.5, added "auto-blank option".
• 0.35 Updated Example5 to meet diskemu.bin v0.9BETA requirements.
• 0.36 Rewrote Example5 to use diskem1x.bin v1.1BETA and cdrpack v1.2 workspace. Much more easier to use!
• 0.37 Rewrote most of the page. Now using cdrpack!
• 0.38 Updated Windows XP section!
• 0.39 Minor overall changes.
• 0.40 Minor changes and cleanup.

• Martin Moens, for hosting this page from december 1999 until november 2001 (for free)!
• Denis (saburovo.com) for currently hosting the nu2 site (also for free)!
• Gary Tong, for writing the first version(s) of diskemu.bin/eltorito.sys
• Everybody who gave me feedback